OpenEdge Data Management:<br />DataServer for ORACLE Security

Release 10.1A: OpenEdge Data Management:
DataServer for ORACLE

Security

Using the DataServer involves following the security guidelines required by both OpenEdge and ORACLE. By default, OpenEdge does not impose security on databases, so at a minimum, you follow the guidelines ORACLE requires for your applications.

OpenEdge security

The OpenEdge database management system has no minimum security requirements. You can, however, impose security features on any OpenEdge database or schema holder. There are four levels of application security you can impose:

Database-connection security.

Schema security.

Compile-time security.

Run-time security.

For more information about compile-time and run-time security, see OpenEdge Deployment: Managing 4GL Applications . For general information about OpenEdge security, see OpenEdge Getting Started: Core Business Services .

ORACLE security

All users must supply a valid user ID and password to access an ORACLE database. In addition, ORACLE provides security in the form of distinct privileges that control access to databases and objects within databases. ORACLE regulates access to database objects at the table level based on types of tasks. For example, INDEX privileges allow the user to create or drop indexes.

The DataServer does not support Trusted ORACLE.

To use the OpenEdge DataServer for ORACLE, there are three security requirements:

To create the schema holder for the ORACLE database, you must have sufficient privileges to connect and create a session and select privileges for system objects in the ORACLE database.

To run DataServer applications that access an ORACLE database, you must have SELECT privileges for the sys.dual system table.

To connect to the schema holder for the ORACLE database, you must supply a valid user ID and password for the target database. OpenEdge provides connection parameters that the DataServer uses to pass this information to the ORACLE Database Manager.

See the "Schema holder security" section for a detailed description of the required privileges.